elmussol

Tue, 30 Jul 2019 17:37:02 -0400 last edited: Wed, 31 Jul 2019 06:09:25 -0400

elmussol

elmussol@elsmussols.net

I intend to do two server tasks this Thursday afternoon.

1: Do a dist-upgrade from Debian Stretch to Debian Buster.

2: Upgrade from PHP7.0 to PHP7.3.

Therefore Hubzilla at elsmussols.net, nextcloud.elsmussols.net and email will be down from about ~~1300CEST (1100UCT)~~ 1500CEST (1300UCT) on Thursday, 01 August 2019. I hope to be down for a maximum of three hours.

update: timeframe moved two hours later (can't turn down paid work).

php debian hubzilla

Tue, 30 Jul 2019 18:29:07 -0400

elmussol

elmussol@elsmussols.net

If all goes tremendously well, there will also be

3: Upgrade Nextcloud 15 > 16

But this not a priority.

Thu, 01 Aug 2019 10:35:31 -0400

elmussol

elmussol@elsmussols.net

1 and 2 completed. 3 is for another day. Please let me know if you have issues.

Thu, 01 Aug 2019 13:24:20 -0400

elmussol

elmussol@elsmussols.net

I wrote:

3 is for another day.

'Tis a lie, I've just done that one too.

PHP7.blech

Sat, 30 Mar 2019 13:48:48 -0400 last edited: Sat, 30 Mar 2019 13:50:10 -0400

elmussol

elmussol@elsmussols.net

!Hubzilla Support Forum I saw this go by and sighed. Not at the HZ devs but at the Debian ones.

core:master commits wrote the following post Fri, 22 Feb 2019 06:52:25 -0500

Update PHP Version check during Setup.
#^Update PHP Version check during Setup.

Hubzilla 4.0 requires PHP7. The oldest still supported PHP branch is 7.1. So check during Setup for PHP >= 7.1. (cherry picked from commit 3f13c85b)

The issue is that Debian Stable is stuck on 7.0. No worries I thought to myself, there will be a 7.1 or 7.2 I can use from backports. No dice. My options are:

1: Stick at PHP7.0, which is EoL and prevents me from upgrading to HZ 4.0.x.

2: Install PHP7.3 from Debian Testing. This is obviously not recommended on a production server that is on a Stable OS for a reason.

The Debian devs have really dropped the ball on this one. Hubzilla can't be the only PHP thang that was on 7.0 and has been bumped to 7.1 and is hosted on Debian Stable.

PHP

show all 23 comments

Fri, 02 Aug 2019 11:34:08 -0400

I do not think, that you will avoid with Docker, that the mails will be forwarded into the Spam folder. The providers forward the mails depends of the content into the Spam folder.

I would not run everything together in one container. Take docker-compose and create with that for every component a separated container. I use docker-compose and created a container for the database, a container for the program hubzilla and a container for the werbserver. Docker-compose starts all together and it will also restart every container separated if it has an error (depends of the configuration in the docker-compose.yml file). The communication between the containers are in a private network in docker-compose. That is like firewalls. Only the webserver can communicate with hubzilla and only hubzilla can communicate with the database.

Fri, 02 Aug 2019 13:01:02 -0400

My point is to avoid all email providers by running your own service, precisely configured for system reporting and user registration - never to be open for public access. If you are to separate the pieces why limit to issues with php, Hubzilla or MySQL, lets do a complete production-grade solution.

For some reasons the importance of email service required by php applications are not emphasized enough, and I am including all php-based software not just Hubzilla. I use Joomla a lot, and Joomla has solid config for external email, not requiring mail() to be used. So my point is, if you are to VPS, docker-compose and virtualize a lot across layers (box to VPS, VPS to Docker Container, Docker Container to Virtualmin for example, 3 layers!) you do better when the email is sitting as close to the hardware as possible. That way you can use email services with confidence... you do not need to rely on all sort of limitations and restrictions from commercial providers... Your email keeps working no mater what virtualization layer you need to rebuild... etc...

By the way, I am not arguing any solution proposed by anyone. I only recommend if you are to implement a production-grade Hubzilla node, first gain full control over every part of the network. The first piece should be a dedicated server with a good IP for email, and some form of virtualization for DNS and LDAP. This of course goes way beyond the scope of the OP but I cannot help myself mentioning it. Disroot, the Internet Society, the EFF are few of many entities advocating becoming your own server operator, and they also believe the only right way to do it is by implementing every and all recommended internet standards.

I never used Docker before, let alone docker-compose, but I am going to start using it soon. So far I used LXC and LXD cluster with MAAS on my local networks, so I am going to love Docker for sure. Docker-composer sounds promising, and I am going to give it a try on AWS or GAE. Virtualmin also have support for AWS, GCE, and Docker so production-grade use is guaranteed.

DISCLAIMER: Factory 4.0 Open Initiative, LLC does not own any Copyright, Trademark, Intellectual Property or other Non-Materialized Asset. We use GPL v3, CC BY 4.0 or compatible licensing for all content created and maintained by us. We rely on You, the Property Owners of Copyright, Trademark and other Intellectual Property to release and maintain Your Own Terms of Use and Service Agreement. We pledge to observe and respect Your Terms of Use and Service Agreement published by You, the Property Owners. In a few cases where we do not agree with Your Terms of Use and Service Agreement we pledge to stop using the Product and / or Service, and pledge to destroy all instances and copies of Your Non-Materialized Asset under our control. (Last updated on 23 April 2019).

Fri, 02 Aug 2019 13:14:53 -0400

@Introduction

Since php mail() for registration keeps ending up in spam folders a fully configured mail service (DKIM, DMARC, SFP) is a must

You can use any active mail account with Hubzilla via phpmailer addon as well.